Search engine cache control

ABSTRACT

A search query containing at least one term is received at a search controller from a query server and preferably normalized and hashed into a representation of the search query. The representation of the search query is transmitted towards a cache containing multiple query result entries. Each query result entry contains a list of documents associated with the previously searched search query. The cache is then searched and query result entries for the search query are sent to the search controller from the cache. Subsequently, it is determined whether the query result entries are current versions for the search query. If the query result entries are not the current versions, then current versions of the query result entries are obtained.

FIELD OF THE INVENTION

The present invention relates to search engines, such as Internet and intranet search engines, and in particular the present invention relates to search engine cache control.

BACKGROUND

Most people searching the World Wide Web (WWW) use search engines that are designed to help locate information stored on Web sites. Most, if not all, search engines search the WWW for one or more words, phrases, and/or combinations of words or phrases (hereinafter “term” or “terms”), keep an index of the located terms and where they were located, and allow users to look for terms in the index.

To index the billions of Web pages that exist on the WWW, a search engine's “web crawler” locates and downloads Web pages, graphics, audio, video, or other data files (hereinafter “documents”). The search engine's indexing modules or engines then process the downloaded documents, creating an index of terms found in those documents, such as terms on a Web page, the name of the located document itself, or the path where the document is located. In some embodiments, the indexing modules may ignore insignificant terms and may include in the index information about where in the document each indexed term is located.

The index created by the search engine is especially used to identify documents that contain search terms. To search for documents on a particular subject, a user enters or otherwise specifies a search query containing a term and submits the search query to the search engine. The search engine then searches its index to identify documents that contain the term specified by the search query. If the index contains a very large number of documents that satisfy the search query, for example, more than a thousand documents, the search engine may utilize various mechanisms to truncate the search or to otherwise limit the number of documents identified by the search. In any case, each document located by the search engine in response to the search result (excluding those documents which satisfy the query but are not included in the search results) is given a rank or score, otherwise know as the “query rank,” based on the perceived relevance of the document query. A search result listing the located documents, ordered by query rank, is then presented to the user. In other words, the documents with the best (e.g., highest) query ranks are presented first in the search result listing, followed by documents having lower query ranks. In addition, it should be understood that the search result listing generally includes a listing of documents that satisfy the search query, not the documents themselves. The search query listing will typically include for each listed document a title or other identifying information extracted from the document, a link (sometimes called a hyperlink or anchor tag) to the document, and a “snippet” of text to help the user decide whether to view the document. A snippet is a portion of text from a document that contains the search term. For example, “ . . . Computer-Flagship magazine of the IEEE Computer Society, where computing practitioners, . . . ” contains the search term “IEEE.”

Furthermore, as the WWW expands and the universe of documents grows, so does the size of the index. A large index generally takes longer to search than a smaller index. Accordingly, a system and method that increases search efficiency, while returning the most currently indexed search results within an acceptable time period would be highly desirable.

SUMMARY

In a method of searching a document database, a version number or datestamp is associated with each document in a list of documents or document index. A search query containing at least one term is received at a search controller from a query server and preferably normalized and hashed into a representation of the search query. The representation of the search query is transmitted towards a cache containing multiple query result entries. Each query result entry contains a list of documents associated with the previously searched search query. The cache is then searched and query result entries for the search query are sent to the search controller from the cache. Subsequently, it is determined whether the query result entries are current versions for the search query. If the query result entries are not the current versions, then current versions of the query result entries are obtained.

Snippet entries are then requested from the cache corresponding to the query result entries obtained from the cache. Once the snippet entries are received from the cache, it is determined whether the snippet entries are current for the search query. If the snippet entries are not current, the current snippet entries are obtained from documents in which terms from the search query are located. If the snippet entries are current, then duplicate snippets are removed, the remainder of the snippets are sorted and sent to the query server for onward transmittal to the user that submitted the search query.

In another aspect of the invention there is provided a system for searching a document database. The system may include a query server, a cache, a search controller, a document index, and a document database. The cache preferably contains multiple query result entries. Each query result entry contains a list of document identifiers or URLs associated with a previously searched search query. The search controller preferably includes a version table identifying current versions of indexed documents. The search controller also preferably includes communication procedures for receiving a search query containing at least one term, transmitting a representation of the search query towards the cache, and receiving at least one query result entry for the search query from the cache. In addition, the search controller preferably includes instructions for determining whether the at least one query result entry is a current version for the search query, and instructions for obtaining the current version of the at least one query result entry, if the at least one query result entry is not the current version.

Accordingly, search efficiency is improved by searching a cache of previous search results before searching the entire document index, while ensuring that the most currently indexed search results are returned to a user.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the nature and objects of the invention, reference should be made to the following detailed description, taken in conjunction with the accompanying drawings, in which:

FIG. 1 is a block diagram of a search engine system, according to an embodiment of the invention;

FIG. 2 is a block diagram of the search controller shown in FIG. 1;

FIG. 3 is a block diagram of the cache shown in FIG. 1;

FIG. 4 is a schematic representation of a search query being mapped into the cache, according to an embodiment of the invention;

FIG. 5 is a block diagram of a query result entry stored in the cache shown in FIG. 3;

FIG. 6 is a block diagram of a snippet block stored in the cache shown in FIG. 3; and

FIGS. 7A-7E are flow charts of a method for performing a search, according to an embodiment of the invention.

Like reference numerals refer to corresponding elements, components or steps throughout the several views of the drawings.

DESCRIPTION OF EMBODIMENTS

The efficiency and cost of performing a search is dependent on a number of factors, such as the various combinations of keywords used in the search, the length of time spent on the search, the number of documents indexed, etc. The average response time and cost of a search is lowered by storing the search results of previously requested search queries in a temporary storage or cache of a search engine system. One of the benefits of keeping a cache of commonly searched information is that it ensures a fast response to subsequent search queries for the same information, as it takes less time to retrieve the information from local memory. Another benefit of caching commonly searched information is to reduce the cost of servicing multiple search queries requesting the same information. When the result of a search query is cached, there is no need to perform another search of the document index, which may be distributed over multiple disks and memory arrays on multiple remote computer servers. Retrieving such information from the multiple disks and memory arrays in multiple remote computer servers requires significantly more time and resources than retrieving the information from the cache. Accordingly, the systems and methods described below increase search efficiency by using a cache and returning the most recently indexed search results.

FIG. 1 illustrates an embodiment of a search engine system 100. It should be appreciated that the layout of the search engine system 100 is merely exemplary and may take on any other suitable layout or configuration. The search engine system 100 is used to search an index of documents, such as billions of Web pages or other documents indexed by modern search engines.

Note that the search engine system 100 can be used as an Internet search engine, for locating documents on the World Wide Web, or as an Intranet search engine, for locating documents stored on servers or other hosts within an Intranet. In addition, the methodology described herein is applicable to implementations where only portions of documents, such as titles and abstracts, are stored in the database of the search engine system.

The search engine system 100 includes multiple datacenters each housing a backend 105. The datacenters are generally widely dispersed from one another, such as across the continental United States. Search queries submitted by users to the search engine system are routed to an appropriate backend 105 as part of the Domain Name System (DNS), based on current load, geographic locality, whether that datacenter is operating, etc.

Each backend 105 preferably includes multiple query servers 104 coupled to a network 118. The network 118 is preferably the Internet, but may also be any local area network (LAN), wide area network (WAN), or the like. In a preferred embodiment, each query server 104 is a Web server that receives search requests and delivers search results in the form of web pages via HTTP, XML, or similar protocols. Alternatively, if a query server 104 is used within a LAN, i.e., internally and not by the public, it may be an intranet server. In essence, the query servers 104 are configured to control the search process, including searching a document index, analyzing and formatting the search results, etc.

Each backend 105 also preferably includes multiple search controllers 106 coupled to the multiple query servers 104. Each of the search controllers 106 is also preferably coupled to a cache 108, a document index 110 and a document database 112. Each search controller 106 is configured to receive requests from a query server 104 and transmit the requests to the cache 108, the document index 110, and the document database 112. The cache 108 is used to increase search efficiency by temporarily storing previously located search results.

Filtering the search results may occur at any level in the system 100. For example, the search controller 106 may be configured to remove any duplicate entries from the search results received from the index 110, and to collate these lists into a single list of search results. In some embodiments, a query rank is computed by the index 110 for each document identified as satisfying the search query, excluding any documents not included in the search results due to search truncation. The query rank values for the documents in the search results are conveyed to the search controller 106 and/or query server 104, and are used to construct an ordered search result list. Once the search controller 106 constructs the ordered search result list, the search controller 106 transmits the result list to the query server 104, which transmits to the document database 112 a request for snippets of an appropriate subset of the documents in the ordered search list. For instance, the search controller 106 may request snippets for the first fifteen or so of the documents in the ordered search result list. The document database 112 constructs snippets based on the search query, and returns the snippets to the search controller 106. The search controller 106 then returns a list of located documents and snippets back to the query server 104 for onward transmittal to the party requesting the search. Further details of this method are described below in relation to FIGS. 7A-7E.

The index 110 preferably contains an index or database that maps a term to corresponding document identifiers. For example, the index 110 may include an index or database containing a search term “IEEE” and a list of documents, identified by document identifier or URL, in which the term “IEEE” appears. In some embodiments, the index 110 is implemented using a plurality of computers, while in another the index 110 is implemented using a single computer.

The document database 112 stores the documents themselves. Each stored document is indexed by a document identifier. The snippets included in the search results returned by the search engine to a user are obtained from the corresponding documents in the document database 112.

FIG. 2 is a block diagram of one of the search controllers 106 shown in FIG. 1. The search controller 106 preferably includes: at least one data processor or central processing unit (CPU) 204; a memory 218; a communication interface 210 for communicating with the query server 104 (FIG. 1), cache 108 (FIG. 1), index 110 (FIG. 1), and document database 112 (FIG. 1); a power source 202 configured to be coupled to a source of power; and at least one bus 212 that interconnects these components. The search controller 106 may also optionally include one or more user interface devices, such as a monitor 208, and a keyboard/mouse 206.

The memory 218 preferably includes high-speed random access memory and may include non-volatile memory, such as one or more magnetic disk storage devices. The memory 218 preferably stores an operating system 220, such as LINUX, UNIX or WINDOWS, that includes procedures for handling basic system services and for performing hardware dependent tasks. The memory 218 also preferably stores communication procedures 222 used for communicating with the query server 104 (FIG. 1), cache 108 (FIG. 1), index 110 (FIG. 1), and document database 112 (FIG. 1). In particular, the communication procedures 222 are used for receiving search requests from the query server 104 (FIG. 1); transmitting the requests to the cache 108 (FIG. 1) and the index 110 (FIG. 1); receiving lists of search results from the cache 108 or the index 110 (FIG. 1); transmitting lists of search results to the query server 104 (FIG. 1); receiving a request for snippets from the query server; transmitting the request for snippets to the cache or document database 112 (FIG. 1); receiving snippets back from the cache or document database 112 (FIG. 1); and returning the search results, including a list of located documents and snippets, back to the query server 104 (FIG. 1) for onward transmittal to the user device from where the search request was received, as described below in relation to FIGS. 7A-7E.

The memory 218 also preferably includes: search procedures 224 for performing searches of the cache 108 (FIG. 1), index 110 (FIG. 1), and document database 112 (FIG. 1); controller procedures 226 for merging, truncating, removing duplicates, etc.; filter procedures 228 for filtering search results; a hash function 230 that converts a search query into a fixed-sized output or hash value; a version table 232; and a cache 240 for temporarily storing data.

The version table 232 preferably contains a table or array of fields, including segment identifier fields 238, a current version or current datestamp 236 for each segment identifier, and a prior version or prior datestamp 234 for each segment identifier. The segment identifier identifies the portion or segment of all documents that have been indexed or crawled. For example, segment zero (Seg. 0) identifies the first ten thousand documents that have been indexed. The current datestamp indicates the time and/or date when a particular segment was last indexed. For example, segment zero was last indexed or crawled on Sep. 24, 2003. The prior datestamp indicates the second most recent time and/or date when a particular segment was indexed. For example, the previous time that segment zero was indexed or crawled before Sep. 24, 2003, was Sep. 22, 2003.

FIG. 3 is a block diagram of the cache 108 shown in FIG. 1. The cache 108 preferably includes: at least one data processor or central processing unit (CPU) 302; a memory 316; a communication interface 304 for communicating with the search controllers 106 (FIG. 1); a power source 308 configured to be coupled to a source of power; and at least one bus 310 that interconnects these components. The cache 108 may also optionally include one or more user interface devices, such as a monitor 312, and a keyboard/mouse 314.

The cache 108 preferably includes high-speed random access memory and may include non-volatile memory, such as one or more magnetic disk storage devices. The memory 316 preferably stores an operating system 318, such as LINUX, UNIX or WINDOWS, that includes procedures for handling basic system services and for performing hardware dependent tasks. The memory 316 also preferably stores communication procedures 320 used for communicating with the search controller 106 (FIG. 1). In particular, the communication procedures 320 are used for receiving search requests from the search controller 106 (FIG. 1); transmitting results back to the search controller 106 (FIG. 1); receiving requests for snippets from the search controller; and returning snippets back to the search controller, as described below in relation to FIGS. 7A-7E.

The memory 218 also preferably includes: a hash map 324 for mapping the hash value produced by a hash function 322 to the indexed query result entries; a heap 326 of memory that is dynamically allocated and de-allocated on demand; and a local cache 332 for temporarily storing data.

The heap 326 preferably contains query result entries 328 and snippet blocks 330, as described in further detail below in relation to FIGS. 5 and 6.

FIG. 4 is a schematic representation 400 of a search query 402 being mapped into the cache 108 (FIG. 1). Once the search query 402 is received by the cache 108 (FIG. 1), the search query is hashed 404. The hashed search query is then compared to the hash map 406 to locate the relevant cache entry 408 in the heap 326. It should, however, be appreciated that the hash function and hash map lookup may alternatively occur at the search controller.

FIG. 5 is a block diagram of a query result entry 328 stored in the cache 108 (FIG. 1). Each query result entry 328 is specific to a particular search term or phrase, such as “IEEE.” The search query result entry 328(1) preferably contains a header 502 that includes information such as the overall number of documents identifiers (Doc. IDs) listed for the particular query result entry 328(1). For example, one thousand documents may contain the search term “IEEE.” Each query result entry 328 is preferably divided by segment 504. For example, query result entry 1 may contain documents in segments 0, 1, and C, i.e., documents in the first 10000, second 10000, and C^(th) 10000 indexed documents. Each segment 504 preferably contains: a datestamp 506 indicating when the segment containing the list of document stored in the cache was last indexed or crawled, such as on Sep. 24, 2003; the percentage of that segment which was searched 508, such as 95% of the segment was searched and indexed; and a list of the document ID entries (Doc. ID Entries) 510(1)-(A) for documents in that segment that contain the particular search term.

Each document ID entry 510 preferably contains a document identifier (Doc. ID) 516, a rank or score 518 for that document, a bitmap representing the segment in which the document can be located (Seg. Bitmap) 520, as well as other information. The score 518 is preferably a search dependent score or query rank.

FIG. 6 is a block diagram of a snippet block 330 (FIG. 3) stored in the cache 108 (FIG. 1). The snippet block 330(1) preferably contains a header indicating the number of document ID entries (Doc. ID Entries) 602 in the snippet block. The snippet block 330(1) also preferably contains snippet entries 608(1)-(G). Each snippet entry 608 preferably contains a document identifier (Doc. ID) 610, a Segment Number 612 in which that document is located; a segment datestamp 614 indicating when the segment was indexed or crawled; a uniform resource locator (URL) 616 for the document; a title 618 for the document; a size 620 of the document; a snippet 622; as well as other information.

FIGS. 7A-7E are flow charts of a method 700 for performing a search. As the WWW changes continually with documents being added, removed, edited, etc., the documents are preferably re-indexed as often as possible to keep the index current. Newly created indexes are then stored in the index 110 (FIG. 1). As each segment of the documents are indexed, a datestamp of when the indexing occurred is sent from the index 110 (FIG. 1) to the search controller 106 (FIG. 1). The search controller receives these datestamps, at step 704, and stores them in the version table 232 (FIG. 2) as the current datestamp 236 (FIG. 2) for each segment identifier 238 (FIG. 2). The datestamp that was previously the current datestamp is stored as the prior datestamp 234 (FIG. 2). This allows the search controller to respond to a search query with search results that are not the most current, if the system is stressed, such as where too many requests are being received or the index or document database are inoperative.

Initially, a user submits a search query to the system 100 (FIG. 1). The search query is received at a particular backend 105 (FIG. 1) (based on DNS data) and the search request is transmitted to one of the several query servers 104 (FIG. 1) in that datacenter based on a load balancing algorithm. The query server 104 (FIG. 1) receives the search request and transmits the search query to one of the search controllers 106 (FIG. 1), at step 708. The search controller 106 (FIG. 1) receives the search query at step 710, normalizes the query and applies the hash function 230 (FIG. 2) to the normalized query to produce a hash value at step 712. The communication procedures 222 (FIG. 2) then transmit the hash value representing the normalized search query to the cache at step 714. The communication procedures 320 (FIG. 3) in the cache receive the search query hash value at step 716. Alternatively, the query normalization and hashing functions may be performed by the cache.

The hash map 324 (FIG. 3) is then searched for an entry equal to the hash value at step 718. If a matching hash entry is found in the hash map, that entry identifies an entry in the cache that corresponds to the search query (step 720), and that cache entry is retrieved at step 722 so as to obtain a list of document ID entries (Doc. ID), which are then transmitted back to the search controller at step 724. The list of document ID entries is preferably transmitted per segment 504 (FIG. 5). If no results are located, nothing (other than a negative reply) is sent to the search controller, which will proceed to search the index 110 (FIG. 1) in the same manner as if the result list entries were not recent, i.e., step 730—No.

The list of document ID entries are then received by the search controller at step 726. As explained above in relation to FIG. 5, each document ID entry 510 (FIG. 5) preferably contains at least a document identifier (Doc. ID) 516 (FIG. 5) and a bitmap 520 (FIG. 5) of the segment in which the document is located. The search procedures 224 (FIG. 2) in the search controller then compares the segment bitmap 520 (FIG. 54) of each document ID entry 510 (FIG. 5) with the current datestamp 236 (FIG. 2) for that segment number 238 (FIG. 2) at step 728. For example, the segment bitmap may indicate that the Doc. ID Entry 510 (FIG. 5) has a datestamp of Sep. 21, 2003, whereas the current datestamp for segment 1 is Sep. 25, 2003, thereby indicating that Doc. ID Entry 510 (FIG. 5) is not current. Based on the comparison performed at step 728, the search procedures 224 (FIG. 2) determine if the document ID entry is the most recent or current document ID entry at step 730. If the document ID entry is not the most current (730-N), then the search query is transmitted toward the index 110 (FIG. 1) at step 780 (FIG. 7E).

The search query is received by the index 110 (FIG. 1) at step 782. The index is then searched at step 784 and document identifiers located at step 786. A list of located document identifiers corresponding to documents that contain the search term are transmitted back to the search controller at step 788. It should be appreciated that the results preferably contain a list of document identifiers (Doc. IDs), or an indication that no results were located in the index 110 (FIG. 1).

The list of document identifiers is received by the search controller at step 794. The controller procedures 226 (FIG. 2) and filter procedures 228 (FIG. 2) on the search controller then: sorts the list of document identifiers; truncates the list to only include a predetermined amount of document identifiers, such as the top 1000 documents; eliminates duplicates from the list; and/or removes non-relevant document identifiers at step 796.

The search controller then transmits the list of query result entries toward the query server and the cache at step 798. The query result entries are received by the cache at step 790, which stores the list of query result entries at step 792. Similarly, the query server receives the list of query result entries, at step 800, and sends a request for a block of snippets corresponding to the list of document identifiers back to the search controller at step 802. The request for snippets is received by the search controller at step 804, which in turn requests the block of snippets from the cache at step 742 (FIG. 7C). The cache receives the request for the block of snippets at step 744 and searches the heap 326 (FIG. 2) for the requested snippet block 330 (FIG. 3) at step 746. If the block of snippets is located, at step 748, the block is transmitted to the search controller at step 750. If the block of snippets is not located, nothing is sent to the search controller, which proceeds as if not all the snippets were located, i.e., step 756—No.

The block of snippets is then received by the search controller at step 752. The controller procedures 226 (FIG. 2) and filter procedures 228 (FIG. 2) on the search controller then remove any old snippets at step 754. This is accomplished by: comparing the segment datestamp 614 (FIG. 6) for each snippet entry 608 (FIG. 6) against the current datestamp 236 (FIG. 2) for that segment; and then removing snippet entries that are not current. The search procedures 224 (FIG. 2) then determine whether all current snippets have been received at step 756. If all current snippets have been received from the cache (756—Yes), then the snippet entries are sorted and/or any duplicates and non-relevant snippet entries eliminated at step 758. The block of snippet entries is then transmitted to both the query server and cache, at step 760. The query server receives the block of snippet entries and sends them toward the user that made the search request, at step 762. Similarly, the cache receives the block of sorted snippets and stores them for later use at step 761.

If all current snippets have not been received from the cache (756—No), then the search controller requests the current snippets from the document database 112 (FIG. 1), which receives the request as step 741. The document database then searches, at step 743, for the current snippets. If the current snippets are located, at step 745, they are transmitted toward the search controller at step 747.

The current snippets are received by the search controller at step 772. The controller procedures 226 (FIG. 2) and filter procedures 228 (FIG. 2) on the search controller then reorder or sort the current snippets into a block of snippets and/or truncates the block, if necessary, at step 774. The search controller then serves the block of snippets to the query server and the cache at step 776. The query server receives the block of snippets, which are transmitted toward the user device from where the search request came, at step 778. Similarly, the cache receives the block of snippets, at step 781, and stores the block for later use at step 783.

Returning to FIG. 7B, if the search controller received the most current document identifiers (730—Yes), then the document identifiers are merged into a list that is preferably sorted, at step 732. The list of document identifiers are then transmitted, at step 734, toward the query server, which receives them, at step 736, and requests one or more blocks of snippets corresponding to the list of document identifiers to the search controller at step 738. The search controller receives the request for the block of snippets at step 740 and requests the block of snippets from the cache at step 742. The method continues with the cache receiving the request for the block of snippets, at step 744, etc., as described above.

The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated. 

1. A method for searching a document database, comprising: receiving a search query from a client system, said search query containing at least one term; in response to receiving the search query: transmitting a representation of said search query to a cache containing multiple query result entries, where a respective query result entry contains multiple query result segments, each of which comprises a list of documents produced in response to a prior execution of said search query; receiving, for said search query, multiple query result segments from said cache, wherein each query result segment of the multiple query result segments contains a list of documents produced in response to a prior execution of said search query on a distinct segment of the document database, the document database having multiple segments, each segment of the database containing a subset of the documents in the document database; for each respective query result segment received from said cache: determining whether said respective query result segment is a current version for said search query, and in response to determining that the respective query result segment received from said cache is not the current version, executing the search query to obtain the current version of the respective query result segment; and updating the respective query result segment stored in the cache using the obtained current version; and transmitting to the client system information corresponding to at least a portion of the documents listed in the current versions of the received query result segments.
 2. The method of claim 1, further comprising: requesting a snippet entry from said cache corresponding to each received query result segment; and receiving said snippet entry from said cache.
 3. The method of claim 2, further comprising: determining whether said snippet entry is a current version for said search query; and if said snippet entry is not the current version, obtaining the current version of the snippet entry from at least one document in which terms from said search query are located.
 4. The method of claim 2, further comprising: removing said snippet entry if it is not a current version; obtaining the current version of said snippet entry from at least one document in which terms from said search query are located.
 5. The method of claim 1, further comprising, prior to said receiving multiple query result segments, associating a version with each document in the list of documents.
 6. The method of claim 1, further comprising, after said receiving said search query, normalizing said search query.
 7. The method of claim 1, further comprising, after said receiving said search query, hashing said search query.
 8. The method of claim 1, wherein said transmitting said representation further comprises transmitting a normalized and hashed search query to said cache.
 9. The method of claim 1, wherein said determining comprises ascertaining whether said received query result segment has a current datestamp.
 10. The method of claim 9, including obtaining a current query result segment for any query result segment of said multiple query result segments that does not have the current datestamp.
 11. The method of claim 10, wherein said obtaining further comprises: transmitting said search query to a document index corresponding to any query result segment of said multiple query result segments that does not have the current datestamp; and receiving from said document index the current query result segment.
 12. The method of claim 10, further comprising performing at least one operation on the multiple query result segments, said operation selected from a group of operations consisting of: merging contents of said multiple query result segments, removing duplicates from said multiple query result segments, truncating an ordered set of said multiple query result segments, and any combination of the aforementioned operations.
 13. The method of claim 10, further comprising merging contents of said multiple query result segments and performing at least one operation on the merged contents, said operation selected from a group of operations consisting of: removing duplicates from said merged contents; truncating said merged contents, and any combination of the aforementioned operations.
 14. The method of claim 10, further comprising: transmitting a list of documents derived from said multiple query result segments to a query server; and receiving a request for a block of snippet entries from said query server.
 15. The method of claim 14, further comprising: requesting multiple snippet entries from said cache; and receiving multiple snippet entries from said cache.
 16. The method of claim 15, further comprising removing old snippet entries from said multiple snippet entries.
 17. The method of claim 16, further comprising determining whether all requested snippet entries have been received from said cache.
 18. The method of claim 17, further comprising: requesting a remainder of said requested snippet entries from a document database containing documents having terms from said search query therein; and receiving said remainder of said snippet entries.
 19. The method of claim 18, further comprising performing at least one operation on the multiple snippet entries, said operation selected from a group of operations consisting of: reordering said multiple snippet entries, selecting a subset of said multiple snippet entries, and any combination of the aforementioned operations.
 20. The method of claim 18, further comprising transmitting at least a subset of said multiple snippet entries to said query server.
 21. The method of claim 15, further comprising performing at least one operation on the multiple snippet entries, said operation selected from a group of operations consisting of: reordering said multiple snippet entries, selecting a subset of said multiple snippet entries, and any combination of the aforementioned operations.
 22. The method of claim 15, further comprising transmitting at least a subset of said multiple snippet entries to said query server, if all of said multiple snippet entries were located.
 23. A system for searching a document database, comprising: a cache containing multiple query result entries, where each query result entry contains multiple query result segments, each of which comprises a list of documents produced in response to a prior execution of said search query; and a search controller having one or more processors and memory storing one or more programs to be executed by the one or more processors, the search controller including one or more procedures having instructions for: receiving from a client system a search query containing at least one term; in response to receiving the search query: transmitting a representation of said search query to said cache; receiving multiple query result segments for said search query from said cache, wherein each received query result segment contains a list of documents produced in response to a prior execution of said search query, and each query result segment of the multiple query result segments contains a list of documents from a distinct segment of the document database, the document database having multiple segments, each segment of the database containing a subset of the documents in the document database; for each respective query result segment received from the cache: determining whether said respective query result segment is a current version for said search query, and responding to a determination that the respective query result segment received from the cache is not the current version by executing the search query to obtain the current version of the respective query result segment and updating the respective query result segment stored in the cache using the obtained current version; and transmitting to the client system information corresponding to at least a portion of the documents listed in the current versions of the received query result segments.
 24. The system of claim 23, further comprising a query server for receiving said search query from a user, directing said search query to said search controller, receiving search results, and forwarding said search results toward said user.
 25. The system of claim 23, further comprising a document index that collectively contains an index of said documents, and a document database that collectively contains said documents.
 26. The system of claim 23, wherein said search controller further includes instructions for: requesting a snippet entry from said cache corresponding to each received query result segment; and receiving said snippet entry from said cache.
 27. The system of claim 26, wherein said search controller further includes instructions for: determining whether said snippet entry is a current version for said search query; and if said snippet entry is not the current version, obtaining the current version of the snippet entry from at least one document in which terms from said search query are located.
 28. The system of claim 26, wherein said search controller further includes instructions for: removing said snippet entry if it is not a current version; obtaining the current version of said snippet entry from at least one document in which terms from said search query are located.
 29. The system of claim 23, wherein said determining further comprises ascertaining whether each of said multiple query result segments have a current datestamp.
 30. The system of claim 29, wherein said search controller further includes instructions for obtaining a current query result segment for any query result segment of said multiple query result segments that does not have the current datestamp.
 31. The system of claim 30, wherein said instructions for obtaining the current query result segment further comprise instructions for: transmitting said search query to a document index corresponding to any query result segment of said multiple query result segments that does not have the current datestamp; and receiving from said document index the current query result segment.
 32. The system of claim 30, wherein the search controller is further configured to perform at least one operation on the multiple result entries, said operation selected from a group of operations consisting of: merging contents of said multiple query result segments, removing duplicates from said multiple query result segments, truncating an ordered set of said multiple query result segments, and any combination of the aforementioned operations.
 33. The system of claim 30, wherein the search controller is further configured to merge contents of said multiple query result segments and to perform at least one operation on the merged contents, said operation selected from a group of operations consisting of: removing duplicates from said merged contents; truncating said merged contents, and any combination of the aforementioned operations.
 34. The system of claim 30, wherein the search controller is further configured to: transmit a list of documents derived from said multiple query result segments to a query server; and receive a request for a block of snippet entries from said query server.
 35. The system of claim 34, wherein the search controller is further configured to: request multiple snippet entries from said cache; and receive multiple snippet entries from said cache.
 36. The system of claim 35, wherein the search controller is further configured to remove old snippet entries from said multiple snippet entries.
 37. The system of claim 36, wherein the search controller is further configured to determine whether all requested snippet entries have been received from said cache.
 38. The system of claim 37, wherein the search controller is further configured to: request a remainder of said requested snippet entries from a document database containing documents having terms from said search query therein; and receive said remainder of said snippet entries.
 39. The system of claim 38, wherein the search controller is further configured to perform at least one operation on the multiple snippet entries, said operation selected from a group of operations consisting of: reordering said multiple snippet entries, selecting a subset of said multiple snippet entries, and any combination of the aforementioned operations.
 40. The system of claim 38, wherein the search controller is further configured to transmit at least a subset of said multiple snippet entries to said query server.
 41. The system of claim 35, wherein the search controller is further configured to perform at least one operation on the multiple snippet entries, said operation selected from a group of operations consisting of: reordering said multiple snippet entries, selecting a subset of said multiple snippet entries, and any combination of the aforementioned operations.
 42. The system of claim 35, wherein the search controller is further configured to transmit at least a subset of said multiple snippet entries to said query server, if all of said multiple snippet entries were located. 